Multi-agent start already creates isolated agent branches and worktrees, but the launcher panel still sent operators back through cockpit/tmux wording. This adds a Kitty session launcher after every requested lane is created and recorded, so terminal startup remains outside the safety boundary.

Constraint: Branch/worktree creation and lock claiming must remain unchanged before terminal launch
Rejected: Make cockpit/tmux the default launch surface | the requested behavior is one Kitty window for the created agent lanes
Confidence: high
Scope-risk: moderate
Directive: Do not move terminal launch before lane/session creation; terminal failure must never invalidate created lanes
Tested: node --test test/cli-args-dispatch.test.js test/agents-start.test.js test/agents-selection-panel.test.js test/agents-start-dry-run.test.js (30 pass)
Tested: openspec validate agent-codex-kitty-default-agent-terminal-2026-04-30-13-14 --strict
Tested: openspec validate --specs (no spec items found)
Not-tested: live GUI launch in a real Kitty desktop session
Not-tested: npm test remains red with 9 baseline failures outside this touched scope